-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BREAKING CHANGE: (#31) Removing the special nodes classes #33
Conversation
upd: PR updated with the latest master; marked as ready |
ml_pipeline_engine/types.py
Outdated
'vectorize', | ||
'predict', | ||
) | ||
RUN_METHOD_ALIAS = 'process' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still have a question for this method. If we remove the ability to use different names in subclasses, I guess that we actually don't need to remain logic with a method's name as a string. We can just leave the abstract method "process" and use it. It will help understand codebase much faster and less painfully because the method is more explicit than the string name of the method
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok, I've removed the constant, but I decided not to touch any other method dependencies; I suggest we take a look and decide what to eliminate from annotations in the next iteration
diff: edd533b
Related issue:
resolves #31
Changes:
[DataSource, FeatureBase, MLModelBase, FeatureVectorizerBase, EventManagerBase,]
[NodeLike, ProcessorLike, DataSourceLike, FeatureLike, FeatureVectorizerLike, MLModelLike, NodeProtocol,]
[NodeBase.title,]
PipelineChart(..., PipelineChartLike)
andDAGPipelineContext(..., PipelineContextLike):